Conversation
ee646de to
22817c0
Compare
|
I'm having inconclusive regressions. I'm going to re-run the test on current dev and zebra 4.1 |
22817c0 to
07b7b89
Compare
|
Latest run all zebra tests pass |
|
I have ran all tests and all the zebra tests pass (a bunch of zcashd related timeout but those are probably related to the tests being slow) |
|
we have been experiencing differences in results between CI and local testing. have you given the testsuite a run locally? if so, are you managing binaries manually or using "makers container-test"? the latest option is the only one that seems to be reliably passing all tests for us recently. |
|
For CI to run against zebra 4.1.0 the file |
07b7b89 to
8d025f5
Compare
| /// | ||
| /// 1. Detect a payment to your Shielded address | ||
| /// 1. Detect a spend of your Shielded notes | ||
| /// 1. Update your witnesses to generate new spend proofs. | ||
| /// 1. Spend UTXOs associated to t-addresses of your wallet. |
There was a problem hiding this comment.
This change was procedurally generated from a proto file. The compact_formats.proto file still contains the numbers 1. 2. 3. 4. For some reason, proto is now generating 1. 1. 1. 1. This isn't a blocking concern (as it's purely a procedurally-generated comment), but I must admit I am absolutely baffled.
There was a problem hiding this comment.
oh I think MD actually solves the count when rendering.
93c2dcd to
69fd392
Compare
Added CHANGELOG entries and documentation on how to perform this kind of updates update .env.testing-artifacts closes zingolabs#816
Adds sleep statement to allow wallet to sync before `quick_shield`
d8fd938 to
4dcdf06
Compare
Closes #816